Summary

Closes #2351

Extends WolverineParameterAttribute (used by [Aggregate], [WriteAggregate], [ReadAggregate], etc.) with three new ValueSource options for resolving parameter values beyond route arguments and request body properties:

• ValueSource.Header — Resolve from HTTP request headers or Envelope.Headers in message handlers
• ValueSource.Claim — Resolve from ClaimsPrincipal claims (HTTP only, throws in handler context)
• ValueSource.Method — Resolve from the return value of a named static method on the handler/endpoint class, with method injection for its parameters

Convenience properties

// Instead of: [Aggregate(ValueSource = ValueSource.Header, ArgumentName = "X-Tenant-Id")]
[Aggregate(FromHeader = "X-Tenant-Id")]
[Aggregate(FromClaim = "tenant-id")]
[Aggregate(FromMethod = "ResolveId")]
[Aggregate(FromRoute = "orderId")]

Key use case — custom aggregate ID from claims

public static class UpdateConfigEndpoint
{
    public static Guid ResolveId(ClaimsPrincipal user) =>
        Config.CompositeId(user.FindFirst("tenant")?.Value);

    [WolverinePost("/config/update")]
    public static ConfigUpdated Handle(
        UpdateConfig command,
        [Aggregate(FromMethod = "ResolveId")] Config config) => new();
}

Files changed

Test plan

• 18 new handler-level unit tests (Header string/int/Guid, Claim throws, Method discovery/base type/not found, convenience properties)
• 13 new HTTP integration tests (Header string/int/Guid/missing, Claim string/int/Guid/missing, Method Guid/string/default)
• All 1209 CoreTests pass (0 failures)
• All 553 HTTP tests pass (0 failures)

🤖 Generated with Claude Code